|
|
KakaoTalk_20201208_183051427.mp4 (7,663,356 bytes) |
|
|
I have attached speaker picture. |
|
|
Hi please also provide logcat thanks. |
|
|
A possible cause is reproduced. When I do adb disable-verity (which is included in my remount script), files under vendor/factory become invisible. Then when switch A2DP src/sink, BT restart will fail due to missing BT_ADDR file in the folder. After above, BT never work until reboot. |
|
|
Hi jim I will do test more. |
|
|
I will test it on DVT 1 board. Thanks. |
|
|
HI, I can't pair ai2 and swan. Please check it in you side. For test, please check attached image. Thanks. |
|
|
스케치.png (59,917 bytes) |
|
|
Hi Any update ..? |
|
|
Hi Jim, steps) 1. pair with bt speaker. 2. reboot (cold boot) 3. it is not paired automatically. It should be paired automatically. Thanks |
|
|
It is reported by SKB QA. Please check it ASAP. |
|
|
it seems 0001048:0006808 is for 0001151 , can I ignore it here? I'll check the pair state with AI2 after 0001151 done |
|
|
After a brief investigation, this issue is more complicate then I think. 1. ATV discovery only specific CoD, not including AUDIO_VIDEO_SET_TOP_BOX (CoD of AI2) 2. after allowing AUDIO_VIDEO_SET_TOP_BOX, the search result lists a lot, it is not as clear as it used to be. many STB shows, and I have no idea what profile will use and how to make sure all of them can work well if user hit the pair, maybe we should filter them out, but only CoD is checked in the discoverying step. 3. connecting to AI2 will fail because not getting the currect A2DP SINK UUID, I guess it is because SWAN is default in sink mode so AI2 decide not providing SWAN the SINK UUID. I'm not sure if I can fix all above, is it possible to waive this issue? since it seems far from a real user scenario. |
|
|
Hi Mr. Wooshin, the original issue should be fixed so I change the status to resolved. and please create a new ticket If you still need the feature to connect AI2-SINK. |
|
|
Done |
- yk.jung ( (ALTech) Younkwang Jung ) developer
